Skip to content

fix: run MCP tools in the caller project directory #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
BP602 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix: run MCP tools in the caller project directory #14

BP602 wants to merge 1 commit into from

Conversation

@BP602
Copy link

@BP602 BP602 commented Feb 6, 2026 •
edited
Loading

Why

When the proxy was started from its own repository, MCP tools (read/write/edit/bash/glob/grep) inherited the proxy process cwd. OpenCode sessions launched from a different project were then operating on the wrong directory, causing confusion and incorrect file/tool behavior.

What changed

  • MCP tools now resolve relative paths from CLAUDE_PROXY_WORKDIR when set
  • fallback remains process.cwd() for backward compatibility
  • README updated to document CLAUDE_PROXY_WORKDIR

Result

  • proxy can run from one location while tools correctly target the intended project
  • predictable per-project behavior without relocating the proxy checkout

@BP602 BP602 changed the title fix: make MCP tool working directory configurable fix: run MCP tools in the caller project directory Feb 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@BP602